Techniques to manage wireless connections

ABSTRACT

A system, apparatus, method and article to manage wireless connections are described. The apparatus may include a connection management module to automatically form a first connection between a first mobile device and a second mobile device, and a second connection between the second mobile device and a fixed device, wherein the first mobile device is to communicate information with the fixed device using the first and second connections. Other embodiments are described and claimed.

BACKGROUND

A wireless device may be arranged to communicate information using awireless medium, such as radio-frequency (RF) spectrum. In some cases,the operations needed to establish the connection over the wirelessmedium may be relatively complex. Techniques to reduce the complexity ofmanaging wireless connections may facilitate use of the wireless device.Consequently, improvements in managing wireless connections may improvethe use and performance of a wireless device or network.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a block diagram of a system in accordance with oneembodiment.

FIG. 2 illustrates a block diagram of a first node in accordance withone embodiment.

FIG. 3 illustrates a block diagram of a second node in accordance withone embodiment.

FIG. 4 illustrates a block diagram of a connection management module inaccordance with one embodiment.

FIG. 5 illustrates a logic diagram in accordance with one embodiment.

DETAILED DESCRIPTION

FIG. 1 illustrates a block diagram of a system 100. System 100 maycomprise, for example, a communication system having multiple nodes. Anode may comprise any physical or logical entity having a unique addressin system 100. Examples of a node may include, but are not necessarilylimited to, a computer, server, workstation, notebook computer, handheldcomputer, telephone, cellular telephone, personal digital assistant(PDA), combination cellular telephone and PDA, and so forth. The uniqueaddress may comprise, for example, a network address such as an InternetProtocol (IP) address, a device address such as a Media Access Control(MAC) address, and so forth. The embodiments are not limited in thiscontext.

The nodes of system 100 may be arranged to communicate different typesof information, such as media information and control information. Mediainformation is used herein in a very general sense and may refer to anydata representing content meant for a user, such as voice information,video information, audio information, text information, numericalinformation, alphanumeric symbols, graphics, images, symbols, and soforth. Control information is also used herein in a very general senseand may refer to any data representing commands, instructions or controlwords meant for an automated system. For example, control informationmay be used to route media information through a system, or instruct anode to process the media information in a certain manner. Theembodiments are not limited in this context.

The nodes of system 100 may communicate media and control information inaccordance with one or more protocols. A protocol may comprise a set ofpredefined rules or instructions to control how the nodes communicateinformation between each other. The protocol may be defined by one ormore protocol standards as promulgated by a standards organization, suchas the Internet Engineering Task Force (IETF), InternationalTelecommunications Union (ITU), the Institute of Electrical andElectronics Engineers (IEEE), and so forth. The embodiments are notlimited in this context.

System 100 may be implemented as a wired communication system, awireless communication system, or a combination of both. Although system100 may be illustrated using a particular communications media by way ofexample, it may be appreciated that the principles and techniquesdiscussed herein may be implemented using any type of communicationmedia and accompanying technology. The embodiments are not limited inthis context.

When implemented as a wired system, for example, system 100 may includeone or more nodes arranged to communicate information over one or morewired communications media. Examples of wired communications media mayinclude a wire, cable, printed circuit board (PCB), backplane, switchfabric, semiconductor material, twisted-pair wire, co-axial cable, fiberoptics, and so forth. The communications media may be connected to anode using an input/output (I/O) adapter. The I/O adapter may bearranged to operate with any suitable technique for controllinginformation signals between nodes using a desired set of communicationsprotocols, services or operating procedures. The I/O adapter may alsoinclude the appropriate physical connectors to connect the I/O adapterwith a corresponding communications medium. Examples of an I/O adaptermay include a network interface, a network interface card (NIC), disccontroller, video controller, audio controller, and so forth. Theembodiments are not limited in this context.

When implemented as a wireless system, for example, system 100 mayinclude one or more wireless nodes arranged to communicate informationover one or more types of wireless communication media, sometimesreferred to herein as wireless shared media. An example of a wirelesscommunication media may include portions of a wireless spectrum, such asthe RF spectrum. The wireless nodes may include components andinterfaces suitable for communicating information signals over thedesignated wireless spectrum, such as one or more antennas, wirelesstransmitters/receivers (“transceivers”), amplifiers, filters, controllogic, and so forth. The embodiments are not limited in this context.

Some embodiments may be directed to managing connections for a wirelessnetwork, such as system 100. More particularly, the embodiments mayattempt to provide and manage data communication connections between amobile device (e.g., a notebook computer) and a cellular radiotelephonesystem accessed via a handheld device (e.g., a cellular telephone). Inone embodiment, for example, a secure connection may be establishedbetween the notebook computer and the cellular telephone using variouspersonal area network (PAN) techniques. The cellular telephone mayprovide access to data communication services over the cellularradiotelephone system. In this manner, a user with a notebook computermay have access to seamless data communication services over a PAN andwireless wide area network (WWAN) using a cellular telephone. This maybe particularly desirable in the absence of more conventional datacommunication service providers, such as a wireless local area network(WLAN), for example. The embodiments are not limited in this context.

In some embodiments the connections may be managed by a connectionmanagement module (CMM). In one embodiment, for example, the CMM may bearranged to automatically form a first connection between a first mobiledevice and a second mobile device, and a second connection between saidsecond mobile device and a fixed device. The term “automatically” asused herein may refer to performing operations without user interventionor with limited user intervention. The first mobile device maycommunicate information with the fixed device using the first and secondconnections. In one embodiment, the first and second mobile devices mayeach include a single button to initiate forming the first and secondconnections. The embodiments are not limited in this context.

Referring again to FIG. 1, system 100 may include one or more nodes102-1-n. Although FIG. 1 is shown with a limited number of nodes in acertain topology, it may be appreciated that system 100 may include moreor less nodes in any type of topology as desired for a givenimplementation. The embodiments are not limited in this context.

In one embodiment, system 100 may include nodes 102-1, 102-2. Nodes102-1, 102-2 may each comprise, for example, mobile devices havingwireless capabilities. Examples for nodes 102-1, 102-2 may include acomputer, server, workstation, notebook computer, handheld computer,telephone, cellular telephone, personal digital assistant (PDA),combination cellular telephone and PDA, and so forth. The embodimentsare not limited in this context.

In one embodiment, for example, node 102-1 may comprise a mobile device,such as a notebook computer. Although some embodiments may be describedwith mobile device 102-1 implemented as a notebook computer by way ofexample, it may be appreciated that other embodiments may be implementedusing other wireless devices as well. The embodiments are not limited inthis context.

In one embodiment, for example, node 102-2 may comprise a mobile device,such as a cellular telephone. Although some embodiments may be describedwith mobile device 102-2 implemented as a cellular telephone by way ofexample, it may be appreciated that other embodiments may be implementedusing other wireless devices as well. The embodiments are not limited inthis context.

In one embodiment, mobile devices 102-1, 102-2 may communicate media andcontrol information using wireless communications medium 106-1. Mobiledevices 102-1, 102-2 may each comprise a wireless transceiver andantennas 104-1, 104-2, respectively. Examples for antennas 104-1, 104-2may include an internal antenna, an omni-directional antenna, a monopoleantenna, a dipole antenna, an end fed antenna, a circularly polarizedantenna, a micro-strip antenna, a diversity antenna, a dual antenna, anantenna array, a helical antenna, and so forth. Although mobile devices102-1, 102-2 are shown in FIG. 1 with single antennas 104-1, 104-2,respectively, it may be appreciated that wireless devices 102-1, 102-2may also include multiple antennas. The use of multiple antennas may beused to provide a spatial division multiple access (SDMA) system or amultiple-input multiple-output (MIMO) system, for example. Theembodiments are not limited in this context.

Communications between mobile devices 102-1, 102-2 may be performed inaccordance with a number of wireless protocols. Examples of wirelessprotocols may include various wireless local area network (WLAN)protocols, including the IEEE 802.xx series of protocols, such as IEEE802.11a/b/g/n, IEEE 802.16, IEEE 802.20, and so forth. Other examples ofwireless protocols may include various WWAN protocols, such as GlobalSystem for Mobile Communications (GSM) cellular radiotelephone systemprotocols with General Packet Radio Service (GPRS), Code DivisionMultiple Access (CDMA) cellular radiotelephone communication systemswith 1xRTT, Enhanced Data Rates for Global Evolution (EDGE) systems, andso forth. Further examples of wireless protocols may include wirelessPAN protocols, such as an Infrared protocol, a protocol from theBluetooth Special Interest Group (SIG) series of protocols, includingBluetooth Specification versions v1.0, v1.1, v1.2, v2.0, v2.0 withEnhanced Data Rate (EDR), as well as one or more Bluetooth Profiles(collectively referred to herein as “Bluetooth Specification”), and soforth. Other suitable protocols may include Ultra Wide Band (UWB),Digital Office (DO), Digital Home, Trusted Platform Module (TPM),ZigBee, and other protocols. The embodiments are not limited in thiscontext.

In one embodiment, for example, mobile devices 102-1, 102-2 may bearranged with the appropriate hardware, software and radio/airinterfaces to communicate data using a wireless PAN technique, such asBluetooth, for example. Although some embodiments may be described withmobile devices 102-1, 102-2 implemented as Bluetooth devices by way ofexample, it may be appreciated that other embodiments may be implementedusing other wireless devices as well. The embodiments are not limited inthis context.

In one embodiment, system 100 may include node 102-3. Node 102-3 maycomprise, for example, a fixed station having wireless capabilities.Examples for node 102-3 may include a wireless access point (AP), basestation or node B, router, switch, hub, gateway, and so forth. In oneembodiment, for example, node 102-3 may comprise a base station or nodeB for a cellular telephone. Although some embodiments may be describedwith node 102-3 implemented as a base station or node B by way ofexample, it may be appreciated that other embodiments may be implementedusing other wireless devices as well. The embodiments are not limited inthis context.

In one embodiment, mobile device 102-2 and fixed station 102-3 maycomprise part of a cellular communication system. Examples of cellularcommunication systems may include CDMA cellular radiotelephonecommunication systems, GSM cellular radiotelephone systems, NorthAmerican Digital Cellular (NADC) cellular radiotelephone systems, TimeDivision Multiple Access (TDMA) cellular radiotelephone systems,Extended-TDMA (E-TDMA) cellular radiotelephone systems, third generation(3G) systems such as Wide-band CDMA (WCDMA), CDMA-2000, Universal MobileTelephone System (UMTS) cellular radiotelephone systems compliant withthe Third-Generation Partnership Project (3GPP), and so forth.Communications between mobile device 102-2 and fixed station 102-3 maybe performed over wireless communication medium 106-2 in accordance witha number of wireless protocols suitable for a given type of cellularsystem.

In addition to voice communication services, mobile device 102-2 andfixed station 102-3 may communicate using a number of different datacommunication services. Examples of cellular data communication systemsoffering data communication services may include a GSM/GPSR system,CDMA/1xRTT system, EDGE system, and so forth. The embodiments are notlimited in this respect.

In one embodiment, for example, mobile device 102-2 and fixed station102-3 may be arranged with the appropriate hardware, software andradio/air interfaces to perform data communications in accordance with aWWAN technique, such as GSM/GPRS, for example. Although some embodimentsmay be described with nodes 102-2, 102-3 implemented as GSM/GPSR devicesby way of example, it may be appreciated that other embodiments may beimplemented using other wireless devices as well. The embodiments arenot limited in this context.

In one embodiment, system 100 may include network 108 connected to node102-3 by wired communications medium 106-3. Network 108 may comprisepart of the same cellular system as mobile device 102-2 and fixedstation 102-3, and may further include additional cellular system nodessuch as mobile stations, base stations, radio network controllers (RNC),mobile services switching centers (MSC), and so forth. In addition,network 108 may comprise additional nodes and connections to othernetworks, including a voice/data network such as the Public SwitchedTelephone Network (PSTN), a packet network such as the Internet, a LAN,a metropolitan area network (MAN), a WAN, enterprise networks, and soforth. The embodiments are not limited in this context.

In general operation, system 100 may provide data communication servicesfrom mobile device 102-1 (e.g., a notebook computer) using a cellularradiotelephone system (e.g., mobile device 102-2 and fixed station102-3). For example, a secure connection may be established betweenmobile devices 102-1, 102-2 using a PAN technique (e.g., Bluetooth).Mobile device 102-2 (e.g., a cellular telephone) may provide access todata communication services over a cellular radiotelephone system (e.g.,GSM/GPRS) via fixed station 102-3 (e.g., a base station). In thismanner, a user may use mobile device 102-1 to seamlessly access datacommunication services using mobile device 102-2 and a WWAN. This may beparticularly desirable when alternative data communication serviceproviders, such as a WLAN, are not available. The embodiments are notlimited in this context.

In order to form a data communication connection between mobile device102-1 and fixed station 102-3, a secure connection between mobiledevices 102-1, 102-2 may need to be established. To form the secureconnection, a set of discovery and authentication operations may need tobe performed. Depending on the type of security protocol used to formthe connection, such discovery and authentication operations may berelative complex. For example, assume discovery operations are performedin accordance with the Bluetooth Specification. During Bluetoothdiscovery operations, two or more Bluetooth devices may agree tocommunicate with one another. This may occur by placing one of thedevices in a discoverable mode. When in discoverable mode, a Bluetoothdevice may be discoverable by other Bluetooth devices. The otherBluetooth device may be placed in a discovery mode. When in discoverymode, a device may discover other Bluetooth devices. The device indiscovery mode searches for devices in discoverable mode, and whenlocated, performs authentication operations to authenticate the identityof the discovered device. When authentication operations are completed,the two devices form a trusted relationship or trusted pair. When onedevice recognizes another device in an established trusted pair, eachdevice automatically accepts subsequent communications, bypassing thediscovery and authentication process that normally occurs duringBluetooth interactions.

Conventional techniques to establish data communication connectionsbetween mobile devices, however, may be unsatisfactory for a number ofreasons. For example, a user may have difficulty understanding which ofthe pair of devices needs to be placed in a discovery mode, and whichneeds to be placed in a discoverable mode. In another example, a usermay have difficulty placing each device in their respective modes. Thismay occur since placing a device in one of the various modes typicallyinvolves software and menu settings, and therefore may require a user totraverse multiple sets of embedded menus. In yet another example, duringauthentication operations, a user may need to enter an authenticationcode into the device placed in discovery mode, as well as the deviceplaced in discoverable mode. This may require the user to performmultiple, and potentially unnecessary, authentication operations.Furthermore, this may require a user to remember a given authenticationcode used for one or both devices. As authentication codes are becominglonger to provide enhanced security, remembering a particularauthentication code may become increasingly difficult. As a result, thenumber and complexity of conventional discovery and authenticationoperations may reduce system performance, as well as overall userconvenience and satisfaction.

Some embodiments may solve these and other problems. In one embodiment,for example, mobile devices 102-1, 102-2 may include connectionmanagement modules (CMM) 110 a, 110 b, respectively. CMM 110 a, 110 bmay be arranged to manage data communication connections for mobiledevices 102-1, 102-2. For example, CMM 110 a, 110 b may cooperate orinteract to form a secure connection between mobile devices 102-1, 102-2over wireless communications medium 106-1. CMM 110 a, 110 b may form thesecure connection by performing discovery and authentication operationsin accordance with a given PAN technique. CMM 110 a, 110 b may alsoprovide configuration parameters needed for communication with a WWANdata communication network. CMM 110 a, 110 b may reduce the number andcomplexity of the operations associated with managing data communicationconnections between multiple wireless devices. Consequently, CMM 110 a,110 b may potentially improve performance of one or more nodes 102-1-nin particular, and the overall performance of system 100 in general.Accordingly, a user may realize enhanced products and services.

FIG. 2 illustrates a block diagram of a node in accordance with oneembodiment of the system. FIG. 2 illustrates a block diagram of a node200 suitable for use with system 100 as described with reference to FIG.1, such as one or more nodes 102-1-n, for example. In one embodiment,for example, node 200 may be representative of mobile device 102-1. Theembodiments are not limited, however, to the example given in FIG. 2.

As shown in FIG. 2, node 200 may comprise multiple elements, such aselements 202-1-p. Elements 202-1-p may comprise, or be implemented as,one or more circuits, components, registers, processors, softwaresubroutines, modules, or any combination thereof, as desired for a givenset of design or performance constraints. Although FIG. 2 shows alimited number of elements by way of example, it can be appreciated thatmore or less elements may be used in element 202-1-p as desired for agiven implementation. The embodiments are not limited in this context.

In one embodiment, node 200 may include an element 202-1. In oneembodiment, for example, element 202-1 may comprise a processor. Forexample, processor 202-1 may be implemented as a general purposeprocessor, such as a general purpose processor made by Intel®Corporation, Santa Clara, Calif. In another example, processor 202-1 mayinclude a dedicated processor, such as a controller, microcontroller,embedded processor, a digital signal processor (DSP), a fieldprogrammable gate array (FPGA), a programmable logic device (PLD), anetwork processor, an I/O processor, and so forth. When node 200 isimplemented for mobile device 102-1, such as a notebook computer,processor 202-1 may comprise a general purpose processor, such as anIntel Pentium® M processor, for example. The embodiments, however, arenot limited in this context.

In one embodiment, node 200 may include an element 202-2. In oneembodiment, for example, element 202-2 may comprise memory. Memory 202-2may include any machine-readable or computer-readable media capable ofstoring data, including both volatile and non-volatile memory. Forexample, memory 202-2 may include read-only memory (ROM), random-accessmemory (RAM), dynamic RAM (DRAM), Double-Data-Rate DRAM (DDRAM),synchronous DRAM (SDRAM), static RAM (SRAM), programmable ROM (PROM),erasable programmable ROM (EPROM), electrically erasable programmableROM (EEPROM), flash memory, polymer memory such as ferroelectric polymermemory, ovonic memory, phase change or ferroelectric memory,silicon-oxide-nitride-oxide-silicon (SONOS) memory, magnetic or opticalcards, or any other type of media suitable for storing information. Itis worthy to note that some portion or all of memory 202-2 may beincluded on the same integrated circuit as processor 202-1, oralternatively some portion or all of memory 202-2 may be disposed on anintegrated circuit or other medium, for example a hard disk drive, thatis external to the integrated circuit of processor 202-1. Theembodiments are not limited in this context.

In one embodiment, node 200 may include an element 202-4. In oneembodiment, for example, element 202-4 may comprise a wireless or radiotransceiver. Wireless transceiver 202-4 may comprise any transceiversuitable for a particular wireless system. In one embodiment, thetransceiver may be implemented as part of a chip set (not shown)associated with processor 202-1. As used herein, the term “transceiver”may be used in a very general sense to include a transmitter, areceiver, or a combination of both. The embodiments are not limited inthis context.

In one embodiment, node 200 may include an element 202-5. In oneembodiment, for example, element 202-5 may be representative of CMM 110a of mobile device 102-1 as described with reference to FIG. 1. CMM202-5 may provide and manage data communication connections for mobiledevice 102-1. For example, CMM 202-5 may form a secure connectionbetween mobile device 102-1 and other wireless devices. CMM 202-5 mayform the secure connection in cooperation with CMM 302-5 of node 300, asdescribed with reference to FIG. 3. In one embodiment, for example, CMM202-5 may form the secure connection by performing discovery andauthentication operations on behalf of mobile device 102-1 in accordancewith a given wireless protocol, security technique, and underlyingtransport layer. Once a secure connection has been established betweenmobile devices 102-1, 102-2, CMM 202-5 may also assist in configuring adata communication connection between mobile device 102-2 and fixedstation 102-3, as well as a data communication connection between mobiledevice 102-1 and fixed station 102-3 via mobile device 102-2. Theembodiments are not limited in this context.

In one embodiment, node 200 may include elements 202-6, 202-7. In oneembodiment, for example, element 202-6 may comprise an I/O circuit, andelement 202-7 may comprise an I/O device. I/O circuit 202-6 may controla number of I/O devices 202-7. Examples of I/O circuit 202-6 may includea disc controller, video controller, audio controller, keyboardcontroller, mouse controller, and so forth. Examples of I/O device 202-7may include a display, monitor, keyboard, keypad, mouse, touchpad, touchscreen, pointer, speakers, and so forth. The embodiments are not limitedin this context.

In one embodiment, elements 202-1-p may be connected by bus 202-3. Whennode 200 is implemented as part of mobile device 102-1, bus 202-3 maycomprise a system bus such as a peripheral component interconnect (PCI)bus defined by a PCI Local Bus Specification. The embodiments are notlimited in this context.

FIG. 3 illustrates a block diagram of a node in accordance with oneembodiment of the system. FIG. 3 illustrates a block diagram of a node300 suitable for use with system 100 as described with reference to FIG.1, such as one or more nodes 102-1-n, for example. In one embodiment,for example, node 300 may be representative of mobile device 102-2. Theembodiments are not limited, however, to the example given in FIG. 3.

As shown in FIG. 3, node 300 may comprise multiple elements, such aselements 302-1-q. Elements 302-1-q may comprise, or be implemented as,one or more circuits, components, registers, processors, softwaresubroutines, modules, or any combination thereof, as desired for a givenset of design or performance constraints. Although FIG. 3 shows alimited number of elements by way of example, it can be appreciated thatmore or less elements may be used in element 302-1-q as desired for agiven implementation. The embodiments are not limited in this context.

In one embodiment, node 300 may have a similar structure to node 200.For example, elements 302-1-7 of node 300 may be similar tocorresponding elements 202-1-7 as described with reference to node 200,with some potential variation as described further below.

In a first variation, when implemented as a wireless device such as acellular telephone, processor 302-1 may be implemented as a lesspowerful processor relative to processor 202-1, which is moreappropriate for the form factor, processing performance, heattolerances, power resources, application types, and other designconstraints suitable for such devices. For example, when node 300 isimplemented for mobile device 102-2, such as a cellular telephone,processor 302-1 may comprise an Intel Personal CommunicationsArchitecture (PCA) processor based on an Intel XScale® (XSC)microarchitecture, such as an Intel PXA255, PXA 26x, PXA 27x, and soforth. The embodiments are not limited in this context.

In a second variation, element 302-5 may be representative of CMM 110 bof mobile device 102-2 as described with reference to FIG. 2. CMM 302-5may provide and manage data communication connections for mobile device102-2. In one embodiment, for example, CMM 302-5 may form a secureconnection between mobile device 102-2 and other wireless devices. CMM302-5 may form the secure connection in cooperation with CMM 202-5 ofnode 200, as described with reference to FIG. 2. In one embodiment, forexample, CMM 302-5 may form the secure connection by performingdiscovery and authentication operations on behalf of mobile device 102-2in accordance with a given wireless protocol, security technique, andunderlying transport layer. Once a secure connection has beenestablished between mobile devices 102-1, 102-2, CMM 302-5 may alsoassist in configuring a data communication connection between mobiledevice 102-2 and fixed station 102-3, as well as a data communicationconnection between mobile device 102-1 and fixed station 102-3 viamobile device 102-2. The embodiments are not limited in this context.

In general operation, CMM 205-5, 302-5 may cooperate to provide andmanage data communication connections between mobile devices 102-1,102-2. In addition, CMM 205-5, 302-5 may cooperate to provide and managedata communication connections between mobile device 102-1 and fixedstation 102-3, as well as between mobile device 102-2 and fixed station102-3. CMM 205-5, 302-5 may be described in more detail with referenceto FIGS. 4 and 5.

FIG. 4 illustrates a block diagram of a node in accordance with oneembodiment of the system. FIG. 4 illustrates a block diagram of a CMM400 suitable for use with system 100 as described with reference toFIG. 1. In one embodiment, for example, CMM 400 may be representative ofCMM 202-5 when implemented as part of mobile device 102-1. In oneembodiment, for example, CMM 400 may be representative of CMM 302-5 whenimplemented as part of mobile device 102-2. The embodiments are notlimited, however, to the example given in FIG. 4.

As shown in FIG. 4, CMM 400 may comprise multiple elements, such aselements 402-1-r. Elements 402-1-r may comprise, or be implemented as,one or more circuits, components, registers, processors, softwaresubroutines, modules, or any combination thereof, as desired for a givenset of design or performance constraints. Although FIG. 4 shows alimited number of elements by way of example, it can be appreciated thatmore or less elements may be used in element 402-1-r as desired for agiven implementation. The embodiments are not limited in this context.

In one embodiment, CMM 400 may include a service discovery module (SDM)402-1. SDM 402-1 may receive as input an activation signal 404.Activation signal 404 may be representative of a signal received from auser via a software or hardware activator. Activation signal 404 maycause SDM 402-1 to begin operations needed to form a data communicationconnection between mobile devices 102-1, 102-2, mobile device 102-1 andfixed station 102-3, and mobile device 102-2 and fixed station 102-3.The embodiments are not limited in this context.

Techniques may be implemented to reduce the complexity of the userinterface between the user and the CMM application through the use ofhardware or software activators to generate activation signal 404. Forexample, a user may be offered the capability of initiating CMMoperations by selecting a software activator, such as a button, icon, ormenu item, to generate activation signal 404. In another example, a usermay use a hardware activator including a hardware structure, such as adedicated button, key, or multiple keys in combination, to generateactivation signal 404. In yet another example, mobile devices 102-1,102-2 may include a voice recognition engine (not shown), and a user maygenerate activation signal 404 using voice commands as received by thevoice recognition engine. The particular activator used to generateactivation signal 404 may vary in accordance with a number of factors,to include a form factor for the device, the type of input device (e.g.,keypad, keyboard, mouse), the screen area for the display, and so forth.The embodiments are not limited in this context.

In one embodiment, for example, the activator may comprise a singlehardware structure such as a button or key on each of mobile devices102-1, 102-2. For example, a user may press a button on mobile device102-1 to initiate a secure connection with mobile device 102-2. The usermay press a button on mobile device 102-2 to complete the secureconnection. Once the activation button is activated on mobile devices102-1, 102-2, CMM 400 may automatically form a first connection betweenmobile devices 102-1, 102-2 without any further user intervention. Inone embodiment, for example, the first connection may comprise a secureconnection. Once the first connection between mobile devices 102-1,102-2 has been established, a second connection may be establishedbetween mobile device 102-2 and fixed station 102-3. In one embodiment,for example, the second connection may comprise a data communicationconnection over a WWAN. Once the data communication connection isestablished between mobile device 102-2 and fixed station 102-3, mobiledevice 102-1 and fixed station 102-3 may communicate over the first andsecond connections. Consequently, the use of a single hardware structureon each of mobile devices 102-1, 102-2 may significantly reduce thecomplexity of forming a data communication connection between thevarious nodes of system 100.

When implemented as part of mobile device 102-1, SDM 402-1 of CMM 400may place mobile device in a discovery mode to begin scanning forwireless devices and associated capabilities within communication rangeof mobile device 102-1 in response to activation signal 404. Forexample, SDM 402-1 may place mobile device 102-1 in a Bluetoothdiscovery mode to discover any Bluetooth devices within range of mobiledevice 102-1. In another example, SDM 402-1 may scan for infrareddevices within detectable range of mobile device 102-1. In yet anotherexample, SDM 402-1 may scan for other notebook computers with wirelesscapabilities within detectable range of mobile device 102-1. SDM 402-1may continue to scan for available devices until a terminating conditionhas occurred, such as discovering at least one device, exceeding atimeout value, receiving an explicit user command to terminate servicediscovery, and so forth. Once SDM 402-1 discovers all of the deviceswith wireless capabilities within communication range of mobile device102-1, SDM 402-1 may pass the list of devices and associatedcapabilities to service selection module (SSM) 402-2.

When implemented as part of mobile device 102-2, SDM 402-1 of CMM 400may place mobile device 102-2 in a discoverable mode in response toactivation signal 404. When in discoverable mode, mobile device 102-2may broadcast device information so that mobile device 102-2 may bediscoverable by other devices operating in discovery mode, such asmobile device 102-1. For example, assume mobile devices 102-1, 102-2 mayoperate in accordance with the Bluetooth Specification. When indiscoverable mode, mobile device 102-2 may broadcast a Bluetooth nameand Bluetooth address to mobile device 102-1.

When implemented as part of mobile device 102-1, SSM 402-2 of CMM 400may receive the list of devices and associated capabilities from SDM402-1. SSM 402-2 may then display or audibly reproduce the list ofdevices and associated capabilities to the user via a display orspeaker, respectively. Each device may have one or more capabilityparameters associated with the device. Examples of capability parametersmay include type of data connection (e.g., GPRS, EDGE, 1xRTT), a dataconnection rate (e.g., 19.2 Kbps through 1 Mbps), security features(e.g., 64-bit SSL, 128-bit SSL), data service provider (e.g., Vodafone,Viag Interkom, T-Mobile, E-Plus, Sprint, ATT), type of device (e.g.,notebook, cellular telephone, PDA), device owner (e.g., user, spouse,co-worker), and so forth. A user may review the available devices andassociated capabilities, and select a device to form the datacommunications connection. Alternatively, SSM 402-2 may use a selectionalgorithm to automatically select a device without user intervention inaccordance with a set of predefined rules. Once a device has beenselected, a device selection signal may be sent to a security managementmodule (SMM) 402-3.

When implemented as part of mobile device 102-1, SMM 402-3 of CMM 400may receive the device selection signal from SSM 402-2. SMM 402-3 mayproceed to form a secure connection with the device indicated by thedevice selection signal. For example, assume mobile device 102-2 is theselected device. SMM 402-3 may attempt to form a secure connectionbetween mobile devices 102-1, 102-2. To form the secure connection, SMM402-3 may be arranged to perform authentication operations betweenmobile devices 102-1, 102-2. For example, assume mobile devices 102-1,102-2 are arranged to form a secure connection in accordance with theBluetooth Specification. In the Bluetooth Specification, for example,authentication operations are based on a challenge-response scheme.Further assume CMM 400 of mobile device 102-1 operates as a verifier.The verifier may send a Link Management Protocol (LMP) Packet Data Unit(PDU) (e.g., LMP_au_rand) that contains a random number to a claimant,such as CMM 400 of mobile device 102-2. The random number may operate asthe challenge for the claimant. The claimant may calculate a responsethat is a function of the challenge, a Bluetooth Device Address(BD_ADDR) for the claimant, and a secret key. The claimant may send aresponse PDU (e.g., LMP_sres) with the calculated response back to theverifier. The verifier then determines whether the response is corrector not. A successful calculation of the authentication responsetypically requires that two devices share a secret cryptographic key,sometimes referred to as a link key.

In the absence of a common link key, CMM 202-5, 302-5 may performauthentication operations referred to as pairing operations on behalf ofmobile devices 102-1, 102-2, respectively. Pairing operations mayrequire use of a Bluetooth Personal Identification Number (PIN) orBluetooth Passkey (collectively referred to herein as a “BluetoothPIN”). The Bluetooth PIN may be used to authenticate two Bluetoothdevices that do not have a common link key or that have not previouslyexchanged link keys between each other. The Bluetooth PIN may be used tocreate a trusted relationship between mobile devices 102-1, 102-2. TheBluetooth PIN is used in the pairing operations to generate the initiallink key (e.g., K_(int)) that is used for further authentication. Mutualauthentication in accordance with LMP authentication may then beperformed to authenticate the identity of mobile devices 102-1, 102-2.Once mobile devices 102-1, 102-2 have a common link key and therebyforming a trusted pair or trusted relationship, subsequentcommunications between mobile devices 102-1, 102-2 may be performedwithout the normal authentication operations typically associated withBluetooth interactions, absent changes in the trusted relationshipbetween mobile devices 102-1, 102-2.

As described above, the discovery and authentication operations asdefined by the Bluetooth Specification may be relatively complex. A usermay initiate a secure connection between mobile devices 102-1, 102-2,however, by merely pressing or activating a single hardware structure,such as a button, a key, or multiple keys pressed in combination. Inresponse to activation signal 404, CMM 400 automatically manages andperforms the discovery and authentication operations to form the secureBluetooth connection between mobile devices 102-1, 102-2. Although someembodiments may be described with mobile devices 102-1, 102-2 forming asecure connection using the Bluetooth Specification, it may beappreciated that other embodiments may be implemented using otherprotocols as well. The underlying wireless protocol, security techniqueand transport layer used to form the secure connection may vary inaccordance with a desired implementation, and the embodiments are notlimited in this context.

Once SMM 402-3 forms a secure connection between mobile devices 102-1,102-2, SMM 402-3 may send an authentication pass signal to aconfiguration module (CM) 402-4. CM 402-4 may assist in configuring adata communication connection between mobile device 102-2 and fixedstation 102-3, as well as a data communication connection between mobiledevice 102-1 and fixed station 102-3 via mobile device 102-2.

A data communication connection between mobile device 102-2 and fixedstation 102-3 may need certain configuration parameters prior to beingestablished. For example, assume mobile device 102-2 and fixed station102-3 use GPRS to perform data communications. Fixed station 102-3typically has an access point name (APN). For mobile device 102-2 tocommunicate with fixed station 102-3, mobile station 102-2 may need tobe configured with the appropriate APN configuration information. Inaddition, the APN configuration information may vary in accordance witha given GPRS service provider. Furthermore, a given APN may vary inaccordance with a type of data communication connection, such as awireless access protocol (WAP) connection, Internet connection, Intranetconnection, and so forth. Potentially adding to the complexity is thatmobile device 102-2 typically roams through various GPRS serviceproviders on a relatively frequency basis.

As a result of this complexity, CM 402-4 may have access to a database402-5. Database 402-5 may store APN configuration information in a datastructure accessible by CM 402-4. Due to the limited memory resourcesavailable with mobile device 102-2, database 402-5 may be implemented aspart of mobile device 102-1 to take advantage of its greater memoryresources. An example of a data structure with APN configurationinformation may be illustrated in the following Table 1.

TABLE 1 User Secondary Operator GPRS APN Name Password Primary DNS DNSD2 Vodafone Web.Vodafone.de Wvl Vodaphone 139.007.030.125139.007.030.126 02 Viag Interkom Internet Vil Viag 195.182.096.028195.182.096.061 D1 T-Mobile Internet.t-dl.de Tdl GPRS 193.254.160.001193.254.160.002 E-Plus Internet.eplus Deplus WAP 212.023.097.002212.023.097.003

Database 402-5 may store a data structure of APN configurationinformation similar to Table 1. In one embodiment, for example, the datastructure for the APN configuration information may comprise anExtensible Markup Language (XML) document. CM 402-4 may access the APNconfiguration information stored in database 402-5 in response tosequence of configuration events between mobile devices 102-1, 102-2, asdescribed in the following example.

Assume database 402-5 stores APN configuration information in an XMLconfiguration document on mobile device 102-1. CM 402-4 of mobile device102-2 may generate a configuration detection/change event message to CM402-4 of mobile device 102-1 in response to a change in GPRS serviceproviders. CM 402-4 of mobile device 102-2 may detect a change in GPRSservice providers using a universal plug-and-play (UPnP) technique. OnceCM 402-4 of mobile device 102-1 receives the change event message, CM402-4 may retrieve the APN configuration information appropriate for agiven GPRS service provider from the XML document, and send theretrieved information to mobile device 102-2. Alternatively, CMM 400 maycause mobile device 102-1 to push the entire XML configuration documentwith the GPRS APN configuration information to CM 402-4 of mobile device102-2. CM 402-4 may use the UPnP Host API interface provided by themobile device 102-2 service to push the XML configuration document for agiven GPRS service provider. CM 402-4 of mobile device 102-2 may thenconfigure the APN for the new GPRS service provider using the APNconfiguration information provided by CM 402-4 of mobile device 102-1.CM 402-2 of mobile device 102-2 may send an APN configuration completedmessage to CM 402-2 of mobile device 102-1 once the new APN has beenappropriately configured.

The XML configuration document may be updated in a number of differentways. For example, in the case of enterprise users (e.g., DigitalOffice), the XML configuration document can be updated when mobiledevice 102-1 is connected to the corporate network. It is expected thatcorporate information technology (IT) maintains the GPRS APN table inthe corporate network to assist enterprise users. The embodiments arenot limited in this context.

In the case of non-enterprise users, the WAP and GPRS configurationsettings may be configured on mobile device 102-2 before connecting to aWWAN for the first time or while roaming. The common communicationsframework (CCF) architecture developed by Intel Corporation may addressthis issue by adopting existing over-the-air (OTA) techniques forconfiguring the APN configuration parameters on mobile device 102-2.Mobile device 102-1 may maintain various short messaging service (SMS)parameters for various service providers which are required to acquiresettings OTA in database 402-5. In addition, database 402-5 may alsomaintain the APN settings that were acquired OTA in the past. The APNsettings may be acquired and configured using SMS in response to variousconfiguration events. For example, the APN parameters may be received inan OTA message by sending an SMS to an OTA settings service number for agiven service provider. The message may comprise a special string (e.g.“NokiaWAP”). The acquired APN configuration information may bemaintained in database 402-5 in mobile device 102-1 since the number ofconfigurable APNs on mobile device 102-2 is typically product dependent.

Operations for the above embodiments may be further described withreference to the following figures and accompanying examples. Some ofthe figures may include a logic flow. Although such figures presentedherein may include a particular logic flow, it can be appreciated thatthe logic flow merely provides an example of how the generalfunctionality as described herein can be implemented. Further, the givenlogic flow does not necessarily have to be executed in the orderpresented unless otherwise indicated. In addition, the given logic flowmay be implemented by a hardware element, a software element executed bya processor, or any combination thereof. The embodiments are not limitedin this context.

FIG. 5 illustrates a logic diagram in accordance with one embodiment.FIG. 5 illustrates a logic flow 500. Logic flow 500 may berepresentative of the operations executed by one or more structuredescribed herein, such as system 100, node 200, node 300, and/or CMM400. As shown in logic flow 500, a first connection may be formedbetween a first mobile device and a second mobile device at block 502. Asecond connection may be formed between the second mobile device and afixed device at block 504. Information may be communicated between thefirst mobile device and the fixed device using the first and secondconnections at block 506.

In one embodiment, a first activation signal may be generated using afirst button on the first mobile device. A second activation signal maybe generated using a second button on the second mobile device. Thefirst and second activation signals may initiate forming the first andsecond connections.

In one embodiment, the first and second connections may be formedwithout user intervention. Alternatively, the first and secondconnections may be formed with limited user intervention. Theembodiments are not limited in this context.

In one embodiment, a set of wireless devices and their associatedcapabilities may be discovered within communication range of the firstmobile device to form a list of wireless devices. The second mobiledevice may be selected from the list of wireless devices based on theassociated capabilities. The second mobile device may be selected by auser or automatically in accordance with a selection algorithm. Thesecond mobile device may be authenticated to form the first connection.The second mobile device may be configured with the appropriateconfiguration information to form the second connection.

Numerous specific details have been set forth herein to provide athorough understanding of the embodiments. It will be understood bythose skilled in the art, however, that the embodiments may be practicedwithout these specific details. In other instances, well-knownoperations, components and circuits have not been described in detail soas not to obscure the embodiments. It can be appreciated that thespecific structural and functional details disclosed herein may berepresentative and do not necessarily limit the scope of theembodiments.

It is also worthy to note that any reference to “one embodiment” or “anembodiment” means that a particular feature, structure, orcharacteristic described in connection with the embodiment is includedin at least one embodiment. The appearances of the phrase “in oneembodiment” in various places in the specification are not necessarilyall referring to the same embodiment.

Some embodiments may be implemented using an architecture that may varyin accordance with any number of factors, such as desired computationalrate, power levels, heat tolerances, processing cycle budget, input datarates, output data rates, memory resources, data bus speeds and otherperformance constraints. For example, an embodiment may be implementedusing software executed by a general-purpose or special-purposeprocessor. In another example, an embodiment may be implemented asdedicated hardware, such as a circuit, an application specificintegrated circuit (ASIC), Programmable Logic Device (PLD) or digitalsignal processor (DSP), and so forth. In yet another example, anembodiment may be implemented by any combination of programmedgeneral-purpose computer components and custom hardware components. Theembodiments are not limited in this context.

Some embodiments may be described using the expression “coupled” and“connected” along with their derivatives. It should be understood thatthese terms are not intended as synonyms for each other. For example,some embodiments may be described using the term “connected” to indicatethat two or more elements are in direct physical or electrical contactwith each other. In another example, some embodiments may be describedusing the term “coupled” to indicate that two or more elements are indirect physical or electrical contact. The term “coupled,” however, mayalso mean that two or more elements are not in direct contact with eachother, but yet still co-operate or interact with each other. Theembodiments are not limited in this context.

Some embodiments may be implemented, for example, using a machine-readable medium or article which may store an instruction or a set ofinstructions that, if executed by a machine, may cause the machine toperform a method and/or operations in accordance with the embodiments.Such a machine may include, for example, any suitable processingplatform, computing platform, computing device, processing device,computing system, processing system, computer, processor, or the like,and may be implemented using any suitable combination of hardware and/orsoftware. The machine- readable medium or article may include, forexample, any suitable type of memory unit, memory device, memoryarticle, memory medium, storage device, storage article, storage mediumand/or storage unit, for example, memory, removable or non-removablemedia, erasable or non-erasable media, writeable or re-writeable media,digital or analog media, hard disk, floppy disk, Compact Disk Read OnlyMemory (CD-ROM), Compact Disk Recordable (CD-R), Compact DiskRewriteable (CD-RW), optical disk, magnetic media, magneto-opticalmedia, removable memory cards or disks, various types of DigitalVersatile Disk (DVD), a tape, a cassette, or the like. The instructionsmay include any suitable type of code, such as source code, compiledcode, interpreted code, executable code, static code, dynamic code, andthe like. The instructions may be implemented using any suitablehigh-level, low-level, object-oriented, visual, compiled and/orinterpreted programming language, such as C, C++, Java, BASIC, Perl,Matlab, Pascal, Visual BASIC, assembly language, machine code, and soforth. The embodiments are not limited in this context.

Unless specifically stated otherwise, it may be appreciated that termssuch as “processing,” “computing,” “calculating,” “determining,” or thelike, refer to the action and/or processes of a computer or computingsystem, or similar electronic computing device, that manipulates and/ortransforms data represented as physical quantities (e.g., electronic)within the computing system's registers and/or memories into other datasimilarly represented as physical quantities within the computingsystem's memories, registers or other such information storage,transmission or display devices. The embodiments are not limited in thiscontext.

While certain features of the embodiments have been illustrated asdescribed herein, many modifications, substitutions, changes andequivalents will now occur to those skilled in the art. It is thereforeto be understood that the appended claims are intended to cover all suchmodifications and changes as fall within the true spirit of theembodiments.

1. An apparatus comprising a connection management module toautomatically form a first connection between a first mobile device anda second mobile device, and a second connection between said secondmobile device and a fixed device, wherein said first mobile device is tocommunicate information with said fixed device using said first andsecond connections.
 2. The apparatus of claim 1, wherein said first andsecond mobile devices each include a single button to initiate formingsaid first and second connections.
 3. The apparatus of claim 1, whereinsaid connection management module is to form said first and secondconnections without user intervention.
 4. The apparatus of claim 1,wherein said first connection is a personal area network connection, andsaid second connection is a wireless wide area network connection. 5.The apparatus of claim 1, wherein said first connection is a secureconnection, and said second connection is a data communicationsconnection.
 6. The apparatus of claim 1, wherein said connectionmanagement module comprises: a service discovery module to discoverwireless devices and associated capabilities within communication rangeof said first mobile device in response to an activation signal, andoutput a list of discovered devices; a service selection module toreceive said list of discovered devices and associated capabilities,select said second mobile device based on said associated capabilities,and output a device selection signal; a security management module toreceive said device select signal, authenticate said second mobiledevice to form said first connection, and output an authentication passsignal; and a configuration module to configure said second mobiledevice with configuration information to form said second connection. 7.A system comprising: an antenna; a transceiver to couple to saidantenna; and a connection management module to couple to saidtransceiver, said connection management module to automatically form afirst connection between a first mobile device and a second mobiledevice, and a second connection between said second mobile device and afixed device, wherein said first mobile device is to communicateinformation with said fixed device using said first and secondconnections.
 8. The system of claim 7, wherein said first and secondmobile devices each include a single button to initiate forming saidfirst and second connections.
 9. The system of claim 7, wherein saidconnection management module to form said first and second connectionswithout user intervention.
 10. The system of claim 7, wherein said firstconnection is a personal area network connection, and said secondconnection is a wireless wide area network connection.
 11. The system ofclaim 7, wherein said first connection is a secure connection, and saidsecond connection is a data communications connection.
 12. The system ofclaim 7, wherein said connection management module comprises: a servicediscovery module to discover wireless devices and associatedcapabilities within communication range of said first mobile device inresponse to an activation signal, and output a list of discovereddevices; a service selection module to receive said list of discovereddevices and associated capabilities, select said second mobile devicebased on said associated capabilities, and output a device selectionsignal; a security management module to receive said device selectsignal, authenticate said second mobile device to form said firstconnection, and output an authentication pass signal; and aconfiguration module to configure said second mobile device withconfiguration information to form said second connection.
 13. A method,comprising: forming a first connection between a first mobile device anda second mobile device; forming a second connection between said secondmobile device and a fixed device; and communicating information betweensaid first mobile device and said fixed device using said first andsecond connections.
 14. The method of claim 13, further comprisinggenerating a first activation signal using a first button on said firstmobile device, and a second activation signal using a second button onsaid second mobile device, said first and second activation signals toinitiate forming said first and second connections.
 15. The method ofclaim 13, wherein said first and second connections are formed withoutuser intervention.
 16. The method of claim 13, further comprising:discovering wireless devices and associated capabilities withincommunication range of said first mobile device to form a list ofwireless devices; selecting said second mobile device from said list ofwireless devices based on said associated capabilities; authenticatingsaid second mobile device to form said first connection; and configuringsaid second mobile device with configuration information to form saidsecond connection.
 17. An article comprising a machine-readable storagemedium containing instructions that if executed enable a system to forma first connection between a first mobile device and a second mobiledevice, form a second connection between said second mobile device and afixed device, and communicate information between said first mobiledevice and said fixed device using said first and second connections.18. The article of claim 17, further comprising instructions that ifexecuted enable the system to generate a first activation signal using afirst button on said first mobile device, and a second activation signalusing a second button on said second mobile device, said first andsecond activation signals to initiate forming said first and secondconnections.
 19. The article of claim 17, further comprisinginstructions that if executed enable the system to form said first andsecond connections without user intervention.
 20. The article of claim17, further comprising instructions that if executed enable the systemto discover wireless devices and associated capabilities withincommunication range of said first mobile device to form a list ofwireless devices, select said second mobile device from said list ofwireless devices based on said associated capabilities, authenticatesaid second mobile device to form said first connection, and configuresaid second mobile device with configuration information to form saidsecond connection.